Hotfix #72102 for PowerSCADA ETL v1.4 

This hotfix includes the following changes:
- Updates to the way the Delimited File Load Task V2 handles inbound data from a 'pair group' extract task such
as the PowerSCADA Extract Task.
- Performance improvements to the grid shown on the Mappings tab when it is first loaded.
- Various performance improvements to the PSE extract task.
- Various performance improvements to the PME load task's supporting logic, and the addition of a new 'pair group' PME load task (the Power Monitoring Expert Bulk Data Load Task) for better performance in large data import scenarios.

Instructions for installing the hotfix:

High Level Instructions:
------------------------
1 - Stop all windows services that are associated with ETL jobs.
2 - Backup the current ETL root folder, and then copy/paste the files from the hotfix zip file into the ETL root folder.
3 - (Optional) - Use ETL's "Run once" feature to run your job a single time and confirm the hotfix was applied as expected.
4 - Restart the windows services that were stopped in step 1 above.

Detailed Instructions:
----------------------
1 - Stop all windows services that are associated with ETL jobs.

First, stop any existing ETL services that were created with PowerSCADA ETL v1.4.
To do this: Open the ETL admin UI (TacticalSolutionsManager.exe) in your installed ETL folder.  
The ETL admin UI can be opened by either using the shortcut on the desktop ("PowerSCADA Expert with Advanced Reports ETL") or 
by browsing to the ETL folder and running TacticalSolutionsManager.exe.
By default, this folder is found at the following location, but it could have been changed during original installation:
C:\Program Files\Schneider Electric\ETL (PowerSCADA)\

After opening the ETL admin UI, use the job selection drop down at the top of the window and the Control page to stop all ETL job services associated with this ETL installation.

For example: 
Select a job in the drop down that has an associated windows service.
Press the Control button.
Press the Stop button to stop the service.  Note: if the Stop button is not enabled, the selected job does not have a windows service that is currently running.
Press the OK button to return the main form.
Repeat the four steps above for each job with an associated windows service.

2 - Backup the current ETL root folder, and then copy/paste the files from the hotfix zip file into the ETL root folder.

Now that all job services are stopped, close the ETL admin UI.
Open the ETL root folder in Windows Explorer.
Create a backup of the entire ETL root folder and place the backup in a separate location.

Copy/paste the files included in this hotfix into the ETL root folder.  

Re-open the ETL admin UI.

Note: if you do not see the CSV Extract Task in the ETL UI after deploying the hotfix, it may be because of the following scenario.

The dll files that make up the hotfix may have been "blocked" by Windows because they came from the internet. This is a common issue for people downloading files from the Internet.  If this is the case, try the following:

First, close the ETL UI if it is open.
 
You must "unblock" each dll file. To unblock it, you need to browse to the folder containing the files in Windows explorer.  Bring up the file's properties (e.g., right-click and select Properties) and then press the Unblock button.

After that, press the OK button and try it again. Open the ETL UI and the CSV Extract Task should now show up.

3 - (Optional) - Use ETL's "Run once" feature to run your job a single time and confirm the hotfix was applied as expected.
This step is optional, but it is often useful to see the job run a single time successfully before restarting the windows service associated with the job.

To run a job a single time:

Select the job in the drop down at the top of the ETL admin UI.
Press the Control button.
Press the "Run Once" button.
Let the job run to completion, and note the job run completion dialog.  
When the job finishes, the UI will show an overall 'success' or 'failure' message and will provide a link to the log folder.
Open the log folder, and examine the error.log file in a text editor.
The newest entries appear at the bottom of this file.  

The newest entry should look something like the following:

[Job Logger Started]
[Job Logger Finished]

If there were errors during the run, they will show up between the 'started' and 'finished' tags.

4 - Restart the windows services that were stopped in step 1 above.

To resume the ETL services that were stopped above, do the following:
Use the Control page and the play button to start any jobs that were stopped earlier.
For example:
Select a job in the drop down that you wish to run as a windows service.
Press the Control button.
Press the Play button to resume the job's service.


A note on the new 'Power Monitoring Expert Bulk Data Load Task':
----------------------------------------------------------------
This task is designed to work with PME 9.0. In many large data import scenarios, this task is typically more performant than the 'Power Monitoring Expert Load Task'.
If using this task to load data into PME 8.0 - 8.2, a stored procedure must be applied to the ION_Data database.
This stored procedure is available alongside this hotfix (in the same Box folder) in a separate package.
